BibDB is DESQview–aware. This means that: (a) BibDB will not
needlessly occupy the CPU while waiting for input (true under WINDOWS 3.x as
well), and (b) BibDB will write to the DESQview video buffer instead of
to the video memory. Thus, the "Writes directly to screen" and the
"Virtualize screen" parameters may be switched off in the DESQview DVP file.
However, under DESQview 386, the mouse driver may not operate satisfactorily
in this mode. Thus, you should either switch the mouse off (specify `nomouse'
in the `desqview' configuration file parameter), or use screen
virtualization anyway if you plan to run BibDB in a small window. You
can also specify in the configuration file that, under DESQview, the default
software mouse cursor be replaced by a hardware cursor. The hardware cursor
is a blinking rectangle, and so can be annoying, but it enables automatic
panning of the visible window over the logical screen, and is quite useful.
Under DESQview/X, BibDB does not display a mouse cursor at all, but uses the
global cursor, and so you can leave virtualization off. However, it has been
reported that BibDB has difficulty using XMS under DESQview/X, since
DESQview/X has a tendency to create ``holes'' in contiguous XMS memory. If
this is the case on your system, you should specify `noxms' in the `desqview'
configuration file parameter in order to avoid its use. EMS memory, however,
does work under DESQview/X.